Distributed orbit modeling and propagation method for a predicted and real-time assisted gps system

ABSTRACT

A mobile device includes a processor for generating a predicted orbital state vector using an initial satellite position and velocity and force model parameters received from a server, the predicted orbital state vector being used to generate satellite navigation data; and a GNSS receiver in communication with the processor for receiving the satellite navigation data; wherein the satellite navigation data is valid for a time period.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/182,273, filed on Jul. 13, 2011 which is a continuation of U.S.patent application Ser. No. 12/536,348, filed on Aug. 5, 2009 which is acontinuation of U.S. patent application Ser. No. 11/740,206, filed onApr. 25, 2007, now issued as U.S. Pat. No. 7,612,712, and claims thebenefit under 35 U.S.C. 119(e) of U.S. Provisional Patent ApplicationNo. 60/745,593 filed on Apr. 25, 2006, all of which are herebyincorporated by reference.

FIELD

The present invention describes a method and apparatus for modeling,predicting, and utilizing satellite orbits with the data processingdistributed between a centralized server and a client. In particular,the invention is applied to the Global Positioning System (GPS)satellites, but is equally applicable to other Global NavigationSatellite Systems (GNSS) as well as other future or planned satellitesystems. The present invention relates to a predicted GPS system in amobile communications network, whereby the predicted GPS client canpropagate satellite orbits from an initial seed dataset provided by apredicted GPS server for several days into the future with minimaldegradation in position accuracy, and utilize the predicted data toassist the GPS chip present on, or coupled with, the device. Thispredictive assistance in turn helps accelerate Time To First Fix (TTFF),optimize position solution calculations and improve the sensitivity ofthe GPS chip present on, or coupled with, the device.

BACKGROUND OF THE INVENTION

The present invention utilizes GPS or other Global Navigation SatelliteSystem (GNSS) orbit predictions to seed orbit propagators embedded inmobile devices with a parameter set that provides the capability topropagate GPS orbits with the fidelity required for accurate navigationin mobile devices. The accuracy of the predictions is limited by thefidelity of the propagator implemented within the mobile device and theinability to precisely model the forces acting on the GPS satellites.The use of GPS to describe the current invention is for convenienceonly. For the purposes of this invention the invention described appliesequally to other GNSS such as GLONASS and Galileo or other future orplanned satellite based positioning systems. The context of a mobileclient to describe the current invention is for convenience only. Forthe purposes of this invention, the invention described applies equallyto any remote clients, whether mobile or fixed.

Satellite positioning and prediction is used extensively in manyapplications Notably, users of the GPS require the positions of the GPSsatellites at the time the ranging signal was transmitted in order tocompute a position solution. Currently this orbit information isprovided by the satellites on the radio frequency (RF) data link in theform of a satellite position model. The model utilizes a Keplerian-likeset of orbital elements, termed the ephemeris, which is valid for alimited time period, typically 4 to 6 hours. The GPS satellitesbroadcast the ephemeris data and the receiver demodulates the ephemerisdata from the RF data link that is continuously monitoring this datastream for an updated ephemeris. The ephemeris data is a model thatallows the user to evaluate a set of equations, the mathematical modelof the fit to an orbit arc, and obtain the satellite position at anytime during the model fit period. Although the model allows theevaluation of the satellite position beyond the 4 to 6 hours ofvalidity, the accuracy degrades asymptotically.

In traditional GPS applications, this method was sufficient because theGPS receivers had unobstructed clear view of the satellites and theevaluation of the ephemeris model put few demands on the computing powerof the receivers. However, in modern applications, such as embedding aGPS receiver within a mobile device such as a mobile phone, the GPSreceiver within the mobile device does not have unobstructed clear viewsof the satellites and must often work in weak signal environments. Thisseverely limits the application of this type of distribution ofsatellite position models because the ephemeris model cannot be reliablyreceived from the satellites.

Current GPS receivers in mobile devices continue to demodulate thebroadcast ephemeris as much as possible similar to traditional GPSreceivers to provide autonomous operation. However, because of the harshoperating environments and the requirement for rapid time to fix, thesereceivers are often provided with assistance or aiding data that enablesrapid time-to-first-fix (TTFF) and increased sensitivity. This techniqueof providing assistance or aid to a GPS is commonly called Assisted orAided GPS (AGPS). A major factor in the decreased time-to-first-fix(TTFF) and increased sensitivity is the removal of the requirement todemodulate the broadcast ephemeris data prior to direct satellite signalacquisition.

Although other types of aiding data are used, such as relative rangeestimates, predictions of which satellites are in view, relativesatellite Doppler offsets, and time and frequency aiding, this inventionis focused on the satellite orbit component of AGPS. For many AGPSsystems, the broadcast ephemeris is provided from a network of GPSreference stations that provide pre-formatted reference data. This datais transformed by an AGPS server into industry standard format and thendelivered to the mobile device over the mobile communications network.These GPS reference stations are located at fixed installations thathave clear unobstructed views of the satellites and can therefore obtainthe broadcast ephemeris and provide that broadcast data over the mobiledevice communications link to the embedded GPS receiver. Although thisis an improvement over the GPS receiver in the mobile devicedemodulating the broadcast ephemeris stream, it puts undue demands onthe GPS receiver within the mobile device to be continuously connectedto and passing data across the mobile communications network.Additionally it requires a real-time connection between the GPSreference stations and the mobile communications network that suppliesthe AGPS data to the mobile. This arrangement of data flowing from theGPS reference station onto the mobile communications network, thenfinally reaching the GPS receiver embedded within the mobile device hasseveral points in the data path that could be unavailable at any giveninstant. The present invention reduces the demands on the connectivityand data transmissions on the mobile communications network and alsomitigates latencies associated with the delivery of the assistance data.

A further enhancement to aiding the GPS receiver in a mobile device isprovided by making ephemeris data for future times available to themobile device. For this process, the satellite orbits are computed usingobservations of satellite position, satellite velocity, range,range-rate, Doppler, or similar measurements. Once an orbit isdetermined from the raw data, then the future positions of thesatellites is determined by propagating the orbit forward withtechniques well known in the art of orbital mechanics. These orbitpredictions are then used to generate so-called synthetic ephemeris inthe same mathematical representation as the broadcast ephemeris. Eachsynthetic ephemeris will cover a 4 to 6 hour block of time for a singlesatellite. To extend the capability beyond the 4 to 6 hour range,multiple synthetic ephemerides are provided. For example, for a singlesatellite, 6 synthetic ephemerides would be provided to describe theorbit for one day. Once the synthetic ephemerides are disseminated tothe GPS receiver within the mobile device, the GPS receiver's knowledgeof the GPS satellite positions does not expire after 4 or 6 hours orafter it loses contact with the mobile communications network. Insteadthe GPS receiver will look to the appropriate time block of ephemerisdata.

The synthetic ephemeris can be provided for as long into the future asthe orbit can be reliably predicted. Typically this prediction period isbetween 1 and 10 days, although longer prediction periods are possible.This synthetic ephemeris method is an improvement over the previoustechniques in that there is less pressure on demodulating the broadcastephemeris data and less real-time overhead data traffic pressure on themobile communications network.

Another vendor, Global Locate, has developed the so called Long TermOrbits (LTO) based on centrally processed future estimates of satelliteposition and velocity. These position and velocity are then fit into adefined time period, typically 4-6 hours, to form a continuous timeperiod of synthetic ephemeris. The synthetic ephemeris is constructedsuch that when supplied to a standard GPS receiver, it mimics standardephemeris data A synthetic ephemeris is then locally retrieved for each4-6 hour interval that the mobile GPS receiver is to operate withoutconnection to the LTO data source. For example, one day of LTO datawould comprise six, 4-hour, synthetic ephemeris data sets for each GPSsatellite. This invention is covered under U.S. Pat. Nos. 6,560,534,6,829,535, 6,651,000, 6,542,820, 6,703,972.

For example, one day of LTO data would comprise six, 4-hour, syntheticephemeris data sets for each GPS satellite. However, conventionalpredicted GPS methods like LTO require dissemination of a large group ofephemeris data sets, typically 40 Kb to 100 Kb, over a mobilecommunications network, each valid for 4 to 6 hours, for each satellite.The current invention significantly reduces the volume of data requiredto be broadcast over the mobile communications network to the order of 2KB or less because it does not transmit pre-generated syntheticephemeris or future estimations of satellite positions and velocities.Rather, the current invention provides the mobile device with an initialsatellite position and velocity, along with some force modelcoefficients, from which the mobile client software can locallypropagate these satellite positions and velocities into the future andlocate generate its own synthetic ephemeris data, as required to supplythe GPS or AGPS device Finally, conventional predicted GPS methods likeLTO are typically proprietary and designed to only work with thevendor's own

AGPS chipset, leading to logistical and provisioning issues. The currentinvention is designed to seamlessly align with existing real-time AGPSindustry standards and thus easily integrate with potentially any AGPSchipset.

Prior art techniques distribute GPS orbit information to a GPS receivervia a mathematical model of the satellite position and velocity over arelatively short period of time, typically 4-6 hours. The GPS receiverwithin the mobile device then evaluates that model as a function of timeto determine the satellite position and velocity. The prior arttechniques do not provide the GPS receiver within the mobile device theability to propagate orbit position and velocity information with therequired accuracy for position computation.

The primary purpose of the GPS ephemeris data is to recover the GPSsatellite position and velocity. The process described above implementsthe following steps: 1) prediction of the GPS satellite position andvelocity into the future, 2) reduction of that prediction to amathematical model, 3) transferring that mathematical model of the GPSsatellite position and velocity to the mobile GPS receiver, and 4) themobile GPS receiver evaluating that mathematical model to recover theGPS satellite position and velocity. The present invention eliminatesthe reduction to and evaluation of the mathematical model described insteps 2) and 3).

Providing estimates of a satellite position and velocity propagated intothe future is well known in the art. For the GPS satellites, thisservice has been provided by the International Geodetic Survey (IGS)since January of 1994. Currently the IGS provides a two day predictionof GPS satellite position and velocity, as the so-called UltraRapidproduct combining 2 days of data with 2 days of predictions with aposition and velocity for each 15 minute interval. These data products,and other IGS data products for GLONASS, GPS clocks, etc, are availablefrom the IGS data repository.

To compute a navigation solution using the GPS satellite orbits, the GPSreceiver must interpolate between the prediction times to the exact timerequired for the particular navigation solution. Therefore, a highdegree of granularity is required in the satellite position and velocityprediction and this is precisely what the IGS supplies. These IGSproducts are commonly used in post-processing where GPS rangemeasurements are collected in the field, then returned to a centrallocation with sufficient data storage and computing power to store andinterpolate the GPS satellite position data The GPS data is not used tocontinue the propagation to future times.

To utilize the IGS-style data products in a mobile device, a relativelylarge amount of orbit data would be transmitted over the mobilecommunications network. A major motivation for the ephemeris model, thesynthetic ephemeris, and the Global Locate LTO implementation is toreduce the amount of data that must be broadcast.

The prior art techniques do not provide the GPS receiver within themobile device the ability to propagate orbital information with therequired accuracy for position computation. Further, the prior artassociated with providing GPS ephemeris data to the mobile device hasbeen constrained to the mathematical model utilized in the live databroadcast from the satellite.

Accordingly, it is an object of the invention to provide a system whichreduces the amount of data required to be transmitted. It is a furtherobject of the invention to provide a GPS receiver within the mobiledevice which can propagate a satellite orbit, removing the dependency ofthe 4 to 6 hour satellite ephemeris model. It is yet a further object ofthe invention to provide a GPS receiver which has the capability topropagate orbits based on the amount of unused computational power thatis available, thus further reducing reliance of the GPS receiver/mobiledevices on the network. It is yet another object of the invention toprovide rapid updates from the mobile communications network forsatellite integrity through small “maintenance data” packets. It is afurther object of the invention to provide the mobile device withimproved integrity determinations. It is a further object of theinvention to closely align with open industry standards and operateacross a variety of AGPS chipsets.

SUMMARY OF THE INVENTION

According to the invention there is provided a distributed orbit andpropagation method for use in a predicted GPS or GNSS system, whichincludes a predicted GPS server (PGPS Server), a source of high accuracyorbit predictions (Orbit Server), a global reference network (GRNServer) providing real-time GPS or GNSS assistance data to the PGPSServer, a predicted GPS client (PGPS Client) running on a deviceequipped with a GPS or AGPS chipset. In response to a request from thePGPS Client, the PGPS Server produces and disseminates to the PGPSClient PGPS Seed Data. The PGPS Client uses the PGPS Seed Data topropagate satellite orbits and calculate associated syntheticephemeredes if required.

The propagated satellite orbits, or their related synthetic ephemeredes,can then be supplied to the mobile device GPS/AGPS chipset, irrespectiveof the GPS/AGPS chipset vendor and over a variety of data format andprotocol options. The PGPS Client optionally includes a micro SecureUser Plane (micro-SUPL) server SUPL is an industry standard fordelivering real-time Assisted-GPS from servers located in a mobileoperator network to mobile devices equipped with the necessary SUPLfirmware and AGPS chipset. The PGPS Client micro-SUPL server therebysimplifies integration of the PGPS Client with the AGPS chip and SUPLfirmware that may already be present on the device.

The PGPS Client Software also enables the PGPS Client Device to become asource of assistance data for other PGPS Client Devices. An example ofthis would be in a peer-to-peer communications context where a PGPSClient Device could relay its PGPS Seed Data or PGPS Seed Update Data toother PGPS Client Devices it is connected with. A variant of thisscenario can take advantage of the presence of a local micro-SUPL serverwithin the PGPS Client Device, whereby the PGPS Client Software canserve other PGPS Client Devices with predicted or real-time assistancedata in the expected and required format.

When the GPS satellites are moved in their orbits for routinemaintenance procedures, orbit predictions provided in advance to a GPSreceiver are in error. Previously, all ephemeris sets beyond the timethe satellite was moved would be invalid and new ephemeredes would needto be provided from to the GPS receiver over the communications network.However, it is recognized that the generalized force parameters thatencompass forces such as drag, solar radiation pressure, out-gassing,etcr remain the same even though the satellite was moved and the orbit,therefore, altered. Thus, apart from occasional force parameter updates,only the position and velocity components need to be updated. Having toupdate only the position and velocity for the satellite results in asignificant network traffic savings when satellite maintenance occursresulting in a different trajectory. The PGPS Seed Data—a knownsatellite orbit vector (i.e. position and velocity at a specific time)coupled with highly optimized force model coefficients—is then used bythe PGPS Client to propagate the orbits from that seed epoch for daysinto the future, typically with a degradation of 1-3 meters per day.

A further reduction in mobile communications network loading is achievedby providing a correction term to the last PGPS Seed Data, a so-calledPGPS Seed Update Data. Advantageously, the PGPS Server also producesSeed Update Data and disseminates it to the PGPS Client. By providingPGPS Seed Update Data, the relative network loading is reduced by asmuch as two orders of magnitude compared to conventional predictive GPStechniques.

Preferably the PGPS Client device is a mobile network connected deviceAlternatively, the PGPS Client may be running on a non-mobile networkconnected device.

Preferably the PGPS Client device contains an onboard GPS/AGPS chipsetand related firmware. The firmware may or may not provide support forAssisted-GPS industry standards such as SUPL. Alternatively, theGPS/AGPS chipset and related firmware may also reside in a peripheraldevice connected to the PGPS Client device.

Advantageously, the PGPS System can process blended standard real-timeassistance data and predictive assistance data.

Advantageously, the PGPS System is flexibly configured to disseminateSeed Data and Seed Update Data over any wireless and wired networks, ina push, poll, automatic or combination thereof, over transport protocolsincluding but not restricted to Internet Protocols such as Hyper TextTransfer Protocol (HTTP), Transmission Control Protocol/InternetProtocol (TCP/IP), User Datagram Protocol (UDP), Wireless ApplicationProtocol (WAP), Short Message Service (SMS) or any appropriate customprotocol.

Advantageously, the PGPS System can automatically update Seed Data andSeed Update Data to ensure the PGPS Client operates with the latestorbit prediction model in the event a Real-Time Integrity (RTI)satellite event occurred.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features and advantages will be apparent from the followingdetailed description, given by way of example, of a preferred embodimenttaken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic view of the Predicted GPS system;

FIG. 2 is a table of the general contents of the PGPS Seed Data set;

FIG. 3 is a table of the general contents of the PGPS Seed Update Dataset;

FIGS. 4A-4C are a set of tables showing a data traffic and accuracydegradation comparison between this PGPS System and a conventionalpredicted GPS system over a typical 7-day period;

FIG. 5 is a table of the navigation model parameters that can bepredicted by a specific orbit propagation model in the system;

FIG. 6 is a schematic diagram showing the different functional layers ofthe PGPS Server;

FIG. 7 is a set of tables showing the PGPS Server Orbit PropagationLayer Outputs;

FIG. 8 is a schematic diagram showing the different functional layers ofthe PGPS Client;

FIG. 9 is a tabular representation of the PGPS Client Orbit PropagationLayer Outputs.

DETAILED DESCRIPTION WITH REFERENCE TO THE DRAWINGS

In the following description, the acronyms used together with theirmeaning are set forth below:

-   AGPS Assisted GPS-   ASN Abstract Syntax Notation One-   DGPS Differential GPS-   GPS Global Positioning System-   GRN Global Reference Network-   H-SLP Home SUPL Location Platform-   HTTP Hypertext Transfer-   IMSI International Mobile Subscriber Identity-   IODE Issue of Data Ephemeris-   IP Internet Protocol-   LCS Location Services-   JPL Jet Propulsion Laboratory-   MIDP Mobile Information Device Profile-   MS Mobile Station-   OMA Open Mobile Alliance-   P-Code Precision Code-   PER Packed Encoding Rules-   PGPS Predicted GPS-   PRN Pseudo Range Number-   RTI Real Time Integrity-   RRC Radio Resource Control-   RRLP Radio Resource LCS Protocol-   SET SUPL Enabled Terminal-   SLP SUPL Location Platform-   SMS Short Message Service-   SUPL Secure User Plan Location-   TCP Transmission Control Protocol-   TTFF Time to First Fix-   TIA Telecommunications Industry Association-   LIRA User Range Accuracy-   UTC Universal Coordinated Time-   V-SLP Visitor SUPL Location Platform-   WAP Wireless Application Protocol-   XML Extensible Markup Language

The preferred embodiment of the present invention, as seen in FIG. 1,consists of two main components; the PGPS Server 10 and the PGPS ClientDevice 20 running the PGPS Client Software 22. The PGPS Server 10 iscoupled to and receives assistance data from the GRN Server 14, a GlobalReference Network. The GRN Server 14 is a collection of interconnectedreference stations around the world that communicate through one or morehubs. Each reference station is coupled to one or more GPS receivers andthus receives the data transmitted by each of the GPS satellitescurrently visible from the reference station's location Collectively,the reference stations in the GRN therefore receive the signals from allGPS satellites in the GPS constellation.

A source of high accuracy orbit prediction is required, of which severaloptions exist. In the embodiment of the present invention, an externalhigh accuracy orbit prediction information is obtained by the PGPSServer 10 from the Orbit Server 12, an example of which is the standardJet Propulsion Laboratory Predictive Orbit (PDO) product. Alternatively,the PGPS Server 10 could receive high accuracy GPS orbit prediction fromany other source.

The PGPS Server 10 communicates with the PGPS Client Device 20 having aPGPS Client Software 22, a GPS or an AGPS (Assisted GPS) Chipset 24,related. Firmware 26. Optionally and shown in dotted lines, the mobiledevice may also have an industry standard SUPL (Secure User Plane)Client 28 The GPS/AGPS Chipset 24 and related Firmware 26 could also belocated on another peripheral device attached to the PGPS Client Device20 on which the PGPS Client Software 22 is running Messages passing overa wireless or wired Communication Network 18 between the PGPS ClientDevice 20 and the PGPS Server 10 are set according to PGPS Protocol 16and include PGPS Seed Data Record 30 or PGPS Seed Update Data Record 36,and optionally, standard AGPS assistance data in the form of RRLP (RadioResource Location services Protocol) Messages, which may include RealTime Integrity (RTI), Navigation Model, Almanac, Universal CoordinatedTime (UTC) Model, Ionospheric, Reference Time, Differential Correctionor other assistance-related messages. The PGPS Client 20 solicits andreceives Predicted GPS messages from the PGPS Server 10 over theCommunications Network 18 according to the PGPS Protocol 16. Using PGPSSeed Data Record 30 and/or PGPS Seed Update Data Record 36 information,it can locally propagate satellite orbits into the future in the form ofOrbit State Vectors 106. The Orbit State Vectors 106 can then be used togenerate associated PGPS Navigation Model Data 42 (i.e. predictedephemeris for each satellite). This data, along with other optional RRLPelements can then be passed on to the GPS/AGPS Chipset 24 & GPS/AGPSFirmware 26 in a couple of typical ways.

The primary and most effective method of linking the PGPS ClientSoftware 22 with the onboard GPS/AGPS Chipset 24 & GPS/AGPS Firmware 26is via a micro-SUPL Server 92 designed to support a subset of the SUPLprotocol SUPL is a standards-based protocol 98 defined by the OpenMobile Alliance (OMA) that employs the user plane of wireless mobilenetworks for transferring GPS assistance data and location information.This transfer is normally done between a mobile device and a standardSUPL AGPS Server 102 in the network. Although SUPL does not explicitlysupport sending messages to an on-board provider of assistance data, thePredicted GPS System in the present case fits into the SUPL model bymimicking the H-SLP/V-SLP (Home SUPL Location Platform/Visitor SUPLLocation Platform) in specific use cases.

Mobile integration efforts effectively amount to adapting the onboardSUPL client Firmware 26 so it becomes configurable and can be “pointed”at the onboard micro-SUPL Server 92 when operating in predictive mode.Other integration options are possible such as more directly interfacingthe PGPS Client Software 22 with the GPS/AGPS Chipset 24 & GPS/AGPSFirmware 26 through their proprietary API'.s

Seed Data Description

The PGPS Seed Data Record 30 sets and their related PGPS Seed UpdateData Record 36 sets are produced and/or updated by the PGPS Server 10 ona periodic basis. The PGPS Seed Data Record 30 is then used by a PGPSClient Software 22 to propagate satellite orbits and optionally generatePGPS Navigation Model Data 42.

The PGPS Seed Data Record 30 set, uniquely identified by its SeedIDnumber, consists of a PGPS Seed Data Orbit State Vector 32 (velocity andX,Y,Z position) for each satellite at the current time epoch, coupledwith several PGPS Seed Data Force Model Parameters 34. The PGPS SeedData Force Model Parameters 34 include solar radiation pressurecoefficient, and empirical acceleration terms at a single epoch. Whilecomputing the PGPS Seed Data Record 30 and PGPS Seed Update Data Record36, the PGPS Server Orbit Propagation Layer 48 effectively locally runsa version of the less accurate PGPS Client Orbit Propagation Layer 86.It can then compare the expected performance of the PGPS Client OrbitPropagation Layer 86 against the high accuracy reference provided by theOrbit Server 12. The PGPS Seed Data Record 30 and PGPS Seed Update DataRecord 36 parameters are thus calculated to minimize or shape theaccuracy degradation over a desired time period. These parameters allowthe PGPS Client Orbit Propagation Layer 86 to propagate the orbits fromthat epoch for days into the future with a tolerable degradation in netposition accuracy of 1-3 meters per day.

The PGPS Seed Data Record 30 Structure is shown in the table of FIG. 2.The preferred embodiment of the present invention allows for the use ofmultiple propagation models, and thus multiple PGPS Seed Data Record 30structures and contents, within the same PGPS System. This enablesprecise tailoring of the predicted GPS data performance against, forexample, applications bandwidth or near versus long-term accuracyrequirements. For example, the PGPS System could generate PGPS Seed DataRecord 30 to yield high accuracy over the first couple of days, or toyield an even accuracy performance over a set number of days, all withina given PGPS Seed Data Record 30 size constraint. Further anticipateduses include GPS/AGPS Chipset 24 vendor-specific orbit propagationmodels and related PGPS Seed Data Record 30, or other high-performancethird party orbit propagation models, thereby enabling third partyinnovation within the PGPS System framework.

Using the preferred embodiment default orbit prediction model, the PGPSSeed Data Record 30 is estimated to be 15,590 bits or 1,949 bytes torepresent the entire 32 satellites constellation. This number can varyif other orbit prediction models are used, but is deemed representativeof the expected data size involved. By contrast, most conventionalPredicted GPS systems require 50 Kb or more for the same representation.

Seed Update Data Description

The PGPS System can work by supplying PGPS Seed Data Record 30 only. Inorder to maintain the highest accuracy, such data can be supplied daily,in effect, resetting the accuracy degradation back up to its best level.The PGPS System can however achieve the same effect by utilizing PGPSSeed Update Data Record 36, an optimized form of the seed that requiresless bandwidth.

Each PGPS Seed Update Data Record 36 uniquely relates to a specific PGPSSeed Data Record 30. The PGPS Seed Update Data Record 36 is a smallerdataset, typically only comprised of PGPS Seed Update Data Orbit StateVectors Parameters 38 (delta factors for the related PGPS Seed DataOrbit State Vectors 32) and PGPS Seed Update Data Force Model Parameters40 (delta factors for the related PGPS Seed Data Force Model Parameters34) at the current epoch. The general contents of the PGPS Seed UpdateData Record 36 are shown in FIG. 3.

The PGPS Client Orbit Propagation Layer 86 can use this informationrelative to the previously provided PGPS Seed Data Record 30 topropagate the orbits from that epoch for days with a tolerabledegradation in accuracy of between 1-3 meters per day.

The PGPS Server 10 manages multiple versions of PGPS Seed Update DataRecord 36, typically one for each previously generated PGPS Seed DataRecord 30 over the configured PGPS Seed Data Record 30 retention window.The PGPS Server 10 can then provide the PGPS Client Software 22 with thelatest PGPS Seed Update Data Record 36 related to the PGPS Seed DataRecord 30 already present on the PGPS Client Software 22. The PGPSClient Orbit Propagation Layer 86 can then utilize the received PGPSSeed Update Data Record 36 to propagate the orbits to the current epochand optionally generate matching PGPS Navigation Model Data 42. Oncepropagated, the PGPS Client Software 22 makes this information availableto the GPS/AGPS Chipset 24 & GPS/AGPS Firmware 26 on the PGPS ClientDevice 20.

Using the preferred embodiment default orbit prediction model, the PGPSSeed Update Data Record 36 set is estimated to be 6,374 bits or 797bytes to represent the entire 32 satellites constellation. This numbercan vary if other orbit prediction models are used, but is deemedrepresentative of the expected data size involved. No such differentialmechanism exists in conventional Predicted GPS systems.

The incorporation of the PGPS Seed Update Data Record 36 featureeffectively helps maintain the highest possible accuracy (i.e. toeffectively resets the degradation back to its best level) in a moredata efficient manner since previously supplied Force Model Parameters34 can easily remain valid for several days.

If a PGPS System uses multiple propagation models, PGPS Seed Update DataRecord 36 can be used to update a related PGPS Seed 30 for eachpropagation model in the manner described above

PGPS Navigation Model Data Description

The PGPS Client Software 22 uses the PGPS Seed Data Record 30 and PGPSSeed Update Data Record 36 to propagate satellite orbits into thefuture. These Orbit State Vectors 106 can also be used to generatematching PGPS Navigation Model Data 42.

FIG. 5 shows a typical PGPS Navigation Model Data 42 record. Thisstructure follows the standard GPS navigation model as described inmobile communications industry standards such as the 3GPP TS44.031—Location Services (LCS); Mobile Station (MS)—Serving MobileLocation Centre (SMSC) Radio Resource LCS Protocol (RRLP) document.

Depending on the orbit propagation model in use, certain parameters inthe PGPS Navigation Model Data 42 record are either predicted, zero orset to a constant value. For the default PGPS System orbit propagationmodel, FIG. 5 shows which parameters are predicted (PGPS NavigationModel Data Predicted Fields 45), set to zero (PGPS Navigation Model DataZeroe'd Fields 46) or set to a suitable constant value (PGPS NavigationModel Data Constant Fields 44) provided within the PGPS Seed Data Record30 or PGPS Seed Update Data Record 36.

The PGPS Navigation Model Data 42 record can then be delivered to theGPS/AGPS Chipset 24 & GPS/AGPS Firmware 26 either via theirvendor-specific APIs or via the PGPS Client micro-SUPL Server 92.

RRLP Data Description

The PGPS Server 10 can optionally be configured to deliver a variety ofreal-time GPS assistance data messages in industry standard RRLP format,including;

Real-Time Integrity (RTI)

Navigation Model

Almanac

UTC model

Ionospheric Model

Reference Time

Differential Corrections

Other message types

The ability to provide real-time GPS assistance data along predicted GPScapability allows for the creation of unique service combinations. Forexample, depending on the PGPS Service Level, the PGPS Server 10 candirectly notify the PGPS Client Software 22 whenever there is a changeto the RTI information. The PGPS Client Software 22 will then downloadthe new RTI and the latest PGPS Seed Data Record 30 or PGPS Seed UpdateData Record 36 message This ensures the resulting predicted information(i.e. Orbit State Vectors 106 and PGPS Navigation Model Data 42) are notsubject to accuracy degradations induced by satellite orbit integrityevents such as maintenance of failure. While Conventional Predicted GPSsystems can also incorporate forms of realtime integrity notifications,an entire new large data file must then also be downloaded to the clientto replace the existing one.

Finally, in a non-standard AGPS environment where there may not be anyexisting AGPS server, the PGPS Server 10 can optionally be configured toincorporate real-time GPS assistance data typically available in a basicAGPS service, namely RTI, Almanac, Ionospheric Model, UTC Model andReference Time, alongside the PGPS Seed Data Record 30 or PGPS SeedUpdate Data Record 36. This assistance data is prepared in the standardRRLP format and delivered as a set of messages that can implement mostof the assistance data elements typically found in a standard AGPSserver. The AGPS Interface Layer 90 can therefore supply the onboardGPS/AGPS Chipset 24 & GPS/AGPS Firmware 26 with this information, ifrequired, via its micro-SUPL Server 92 or through the GPS/AGPS Chipset24 proprietary API.

PGPS Service Levels

The present Predicted GPS System is designed for flexibility and allowsfor tailored service deployments and value-added service options. Thereare currently four service levels:

Basic—The Basic PGPS Service Level operates on a simple client-pollbasis. The PGPS Client Software 22 periodically polls the PGPS Server 10for the latest PGPS Seed Data Record 30 or PGPS Seed Update Data Record36. The PGPS Client Software 22 can then propagate the satellite orbitsand generate PGPS Navigation Model Data 42 (i.e. ephemeredes) for futureepochs. This PGPS Navigation Model Data 42 is then delivered to theGPS/AGPS Chipset 24, either directly through the Firmware 26 API orindirectly, via the micro-SUPL Server 92 and AGPS SUPL Client 28.

Premium—The Premium PGPS service incorporates a real-time mechanismwhereby RTI notifications can be automatically sent to the PGPS ClientDevice 20 via WAP Push. These notifications will prompt the PGPS ClientSoftware 22 to request the latest RTI message along with the latestapplicable PGPS Seed Data Record 30 or PGPS Seed Update Data Record 36.The PGPS Client Software 22 can then make the PGPS Navigation Model Data42 and RTI messages available to the GPS/AGPS Chipset 24, eitherdirectly through the Firmware 26 API or indirectly, via the micro-SUPLServer 92 and AGPS SUPL Client 28.

Advanced—The Advanced PGPS service incorporates a realtime mechanismwhereby PGPS Seed Data Record 30, PGPS Seed Update Data Record 36 andRTI RRLP Messages notifications can be pushed directly to the PGPSMobile Device 20 either via SMS 64 or through other bearers availablewithin the wireless network architecture, for example, WAP PUSH 62. ThePGPS Client Software 22 can then make the PGPS Navigation Model Data 42and RTI messages available to the GPS/AGPS Chipset 24, either directlythrough the Firmware 26 API or indirectly, via the micro-SUPL Server 92and AGPS SUPL Client 28. The Advanced PGPS Service requires deeperintegration with network equipment vendors and mobile operators planningto support the service.

Custom—In the case of mobile systems where there is no standard AGPSenvironment, or in the case of special purpose mobile devices with noSUPL client Firmware 26, the PGPS System can be fully customized tointegrate not only predicted PGPS messages, but also any real-timeassistance RRLP messages. The PGPS Client Software 22 is notified onlywhen new versions of these messages are available, so that the PGPSClient Software 22 does not need to poll the PGPS Server 10 forinformation that may not be relevant. The PGPS Client Software 22 canthen make the PGPS Navigation Model Data 42 and RRLP messages availableto the GPS/AGPS Chipset 24, either directly through the Firmware 26 APIor indirectly, via the micro-SUPL Server 92 and AGPS SUPL Client 28. TheCustom PGPS Service requires deeper integration with network equipmentvendors and mobile operators planning to support the service

Predicted GPS Server

The PGPS GPS Server 10 produces the PGPS Seed Data Record 30 and PGPSSeed Update Data Record 36 and provides it to the PGPS Client Software22 as well as providing RRLP messages to the PGPS Client Software 22. Asseen in FIG. 6, the PGPS Server 10 consists of a PGPS Server OrbitPropagation Layer 48, a PGPS Server Data Management Layer 60, a PGPSServer Service Management Layer 54, and a PGPS Server ConfigurationLayer 52. FIG. 6 shows the different layers of the PGPS Server 10.

The purpose of the PGPS Server Orbit Propagation Layer 48 is to generatethe PGPS Seed Data Record 30 and PGPS Seed Update Data Records 36 neededby the PGPS Client Software 22. While computing the PGPS Seed DataRecord 30 and PGPS Seed Update Data Record 36, the PGPS Server OrbitPropagation Layer 48 effectively also runs a version of the lowerfidelity PGPS Client Orbit Propagation Layer 86. It can then compare theexpected performance of the PGPS Client Software 22 against the highaccuracy reference provided by the Orbit Server 12. The PGPS Seed DataRecord 30 and PGPS Seed Update Data Record 36 parameters are thuscalculated to minimize or shape the accuracy degradation over a desiredtime period. These parameters allow the PGPS Client Software 22 topropagate the orbits from that epoch for days into the future with agraceful degradation in accuracy, for example, 1-3 meters per day.

The preferred embodiment of the present invention allows for the use ofmultiple propagation models, each with its own PGPS Seed Data Record 30and PGPS Seed Update Data Record 36 messages, within the same PGPSSystem. This enables precise tailoring of the PGPS System performancewith respect to, for example, applications bandwidth, client processorcapability, or near versus long-term accuracy requirements. For example,the PGPS System could generate PGPS Seed Data Record 30 to emphasizehigh accuracy over the first couple of days, or to yield a uniformaccuracy performance over a set number of days, all within a given PGPSSeed Data Record 30 size constraint. Further anticipated uses includeGPS/AGPS Chipset 24 vendor-specific orbit propagation models and relatedPGPS Seed Data Record 30, or other high-performance third party orbitpropagation models, thereby enabling third party innovation within thePGPS System framework.

As shown in FIG. 7, in the default configuration, the PGPS Server OrbitPropagation Layer 48 runs once every 4 hours epoch 72. It produces themost current PGPS Seed Data 74 and a PGPS Seed Update Data Record setfor previous PGPS Seed Data sets 72 (i.e. up to n days). Each prior PGPSSeed Data 72 has one corresponding PGPS Seed Update Data Record 80 set.With each new 4 hour epoch 70 when the Orbit Propagation Layer 48 runs,the current PGPS Seed Update Data Record 78 is replaced with a new one74. For example, if the Orbit Propagation Layer 48 was configured togenerate PGPS Seed Update Data Record sets for 4 days in the past, theneach time it runs it would produce one new PGPS Seed Data 74 set andtwenty-four (6 epochs per day=4 days=24) Seed Update Data sets.

FIG. 7 illustrates a graphical representation of the PGPS Seed DataRecord 30 and PGPS Seed Update Data Record 36 that would exist if theCurrent Time 70 is January 23 at 8:05. Every PGPS Seed Update DataRecord ID changes for each 4 hour epoch, while the PGPS Seed Data IDsremain the same. This illustrates how each PGPS Seed Update Data Recordfor a given PGPS Seed Data is regenerated for every epoch 72 interval.

In summary, this functional layer is responsible for the followingtasks:

(1) Accepting external highly accuracy orbit prediction data referencesfrom the Orbit Server 12;

(2) Producing the current PGPS Seed Data 74;

(3) Producing the PGPS Seed Update Data Record 80 for each active PGPSSeed Data 72 generated in the preceding N epochs, where N is the numberof epochs per day times the number of days (in default configuration,N=6 epochs/day.times.4 days=24);

The inputs to this layer are as follows:

(1) Default Orbit Server 12—Standard Predicted Orbit Data from JPL;

(2) Future Orbit Server 12—third party high accuracy predictionreferences;

The outputs of this layer are as follows:

(1) The PGPS Server Current PGPS Seed Data Record 74 for the PGPS ServerCurrent Seed Epoch 70;

(2) PGPS Server Current PGPS Seed Update Data Records 80 for each activePGPS Server Previous PGPS Seed Data Records 72; Data Management Layer

The purpose of the Data Management Layer 30 is to manage and store thedata needed by the PGPS Client Software 22. The key functions of thislayer include:

(1) Receive PGPS Server Previous PGPS Seed Data Records 72, PGPS ServerCurrent PGPS Seed Data Record 74 and PGPS Server Current PGPS SeedUpdate Data Records 80 from the PGPS Server Orbit Propagation Layer 48.

(2) Store each PGPS Server Previous PGPS Seed Data Records 72, PGPSServer Current PGPS Seed Data Record 74 produced by the PGPS ServerOrbit Propagation Layer 48 for up to n days (default n=4);

(3) Store the latest PGPS Server Current PGPS Seed Update Data Records80 for each stored PGPS Server Previous PGPS Seed Data Records 72(default 24, i.e. 4 days.times.6 epochs per day);

(4) Expire PGPS Server Previous PGPS Seed Data Records 72 older than ndays;

(5) Handle requests from the PGPS Server Service Management Layer 54,providing the PGPS Server Current PGPS Seed Data Record or appropriatePGPS Server Current PGPS Seed Update Data Records 80 given the currentPGPS Seed Data Record 30 SeedID supplied by the PGPS Client Software 22;

(6) Receive Real-Time Integrity updates from the GRN Server 14;

(7) Notify the PGPS Server Service Management Layer 54 of changes in theReal-Time Integrity of the satellites;

(8) Handle requests from the PGPS Server Service Management Layer 54 toprovide the current RTI message.

(9) Receive Real-Time Assistance Data from the GRN Server 14;

(10) In cases of RTI:

a. Depending on Service Level, notify the PGPS Server Service ManagementLayer 54 of changes in the Real-Time Integrity of the satellites;

b Handle requests from the PGPS Server Service Management Layer 54 toprovide the current RTI message.

(11) In cases of other Real-Time Assistance Data:

a Depending on Service Level, notify the PGPS Server Service ManagementLayer 54 of changes in the Real-Time Assistance Data of the satellites;

b Handle requests from the PGPS Server Service Management Layer 54 toprovide the Real-Time Assistance Data RRLP messages.

The inputs to this layer are the following:

(1) PGPS Server Current PGPS Seed Update Data Records, PGPS ServerCurrent PGPS Seed Data Record 74;

(2) PGPS Server Current PGPS Seed Update Data Records 80 for each PGPSServer Current PGPS Seed Update Data Records 72;

(3) Real-Time Assistance Data.

The outputs to this layer are the following:

(1) PGPS Server Current PGPS Seed Data Record 74 (if the PGPS ClientSoftware 22 has provided an expired Seed ID or no prior seed);

(2) PGPS Server Current PGPS Seed Update Data Record 80 matched to theclient's existing valid PGPS Seed Data Record 30;

(3) The current Real-Time Assistance Data message in RRLP format.

The Service Management Layer

The purpose of the PGPS Server Service Management Layer 54 is to deliverthe PGPS messages to the PGPS Client Software 22. Depending on theService Level being implemented, this delivery can employ both push andpull technologies as well any transport protocol. The key functions ofthe PGPS Server Service Management Layer 54 include:

(1) Receiving and processing requests from the PGPS Client Software 22.These requests are for PGPS Seed Data Record 30, PGPS Seed Update DataRecord 36 or RRLP Data messages A number of transport protocols optionsare available, including:

PGPS Service Management Layer HTTP Interface 56

PGPS Service Management Layer TCP/IP Interface 58

PGPS Service Management Layer UDP Interface 60

PGPS Service Management Layer WAP PUSH Interface 62

PGPS Service Management Layer SMS Interface 64

PGPS Service Management Layer Others Interface 66

(2) Packaging the PGPS message data according to ASN 1 PER convention;

(3) Sending RTI notifications to PGPS Client Devices 20 subscribing tothe Premium, Advanced or Custom PGPS Service Level

(4) Authenticating subscriber requests for Premium, Advanced or CustomPGPS Service Levels;

(5) Sending the PGPS message to the PGPS Client Software 22 via therequested protocol.

The inputs to this layer are the following:

(1) Requests from the PGPS Client Software 22;

(2) Current PGPS Seed Data 74 from the PGPS Server Data Management Layer50;

(3) Applicable PGPS Seed Update Data Record 80 from the PGPS Server DataManagement Layer 50;

(4) GRN RRLP Data messages from the PGPS Server Data Management Layer50.

The outputs of this layer are the following.

(1) PGPS Server Current PGPS Seed Data Record 74;

(2) Applicable PGPS Server Current PGPS Seed Update Data Record 80;

(3) PGPS notifications for the Premium, Advanced and Custom PGPS ServiceLevel;

(4) RTI RRLP Data messages for the Premium, and Advanced PGPS ServiceLevel;

(5) GRN RRLP Data messages for the Custom PGPS Service LevelConfiguration Layer.

Each layer in the PGPS Server 10 contains specific configurationparameters that govern the operation of the system. The PGPS ServerConfiguration Management Layer 52 key function is to record and applythese parameters to each of the PGPS Server Layers.

Orbit Propagation Layer Configuration

The PGPS Server Orbit Propagation Layer 48 has configurable parametersthat determine how frequently new PGPS Server Current PGPS Seed DataRecord 74 and PGPS Server Current PGPS Seed Update Data Records 80 areproduced and how far into the past PGPS Server Current PGPS Seed UpdateData Records 80 will be produced.

Data Management Layer Configuration

The PGPS Server Data Management Layer 50 determines how far in the pastPGPS Server Previous PGPS Seed Data Records 72 and PGPS Server CurrentPGPS Seed Update Data Records 80 will be managed. Any seeds older thanthis setting will be expired. This parameter is shared with the PGPSServer Orbit Propagation Layer 48.

Service Management Layer Configuration

The PGPS Server Service Management Layer 54 has configurable parametersthat include service level option definitions and the type and locationof the subscriber registration database.

The subscriber registration database is used to authenticate thesubscribers against their respective PGPS Service Level This databasemay be internal to an operator, or from an external tool that allowsregistration of individual clients or group of clients. The databasemaintains basic PGPS subscriber information, as follows:

(1) Client ID: A unique identifier for the client such as IMSI;

(2) Service Level: The service level the client subscribes to;

(3) Service Status: e.g. Active, Inactive, Suspended;

(4) Service Start Date;

(5) Service End Date;

(6) Customer Info;

(7) Network Info (if applicable);

(8) Others; TBD. Predicted GPS Client

The PGPS Client Software 22 runs and resides inside a GPS/AGPS enableddevice, whether the GPS/AGPS Chipset 24 and related GPS/AGPS Firmware 26resides on the same device or on an attached peripheral device. Itreceives data from the PGPS Server 10, propagates satellite orbits andgenerates PGPS Client Pre-Generated Predicted Orbit State Vectors 106and associated PGPS Client Pre-Generated Predicted Navigation Model 108for each PGPS Client Pre-Generated Predicted Data Epochs 104, anddelivers assistance data to the GPS/AGPS Chipset 24 via the GPS/AGPSFirmware 26 API or via the SUPL Client 28 and micro-SUPL Server 92. Asseen FIG. 8 the PGPS Client Software 22 consists of several internalcomponents. It contains a PGPS Client Service Management Layer 82, aPGPS Client Orbit Propagation Layer 86, a PGPS Client Data ManagementLayer 84, a PGPS Client AGPS Interface Layer 90 and a PGPS Clientmicro-SUPL Server Layer 92.

Service Management Layer

The PGPS Client Service Management Layer 82 handles the PGPS Protocol 16and handles data flow to/from the PGPS Client Orbit Propagation Layer 86or PGPS Client Data Management Layer 84. The PGPS Client ServiceManagement Layer 82 includes the following key functions;

(1) Periodically requesting PGPS Seed Data Record 30 and/or PGPS SeedUpdate Data Record 36 messages from the PGPS Server 10;

(2) Receiving PGPS Seed Data Record 30 and/or PGPS Seed Update DataRecord 36 messages from the PGPS Server 10;

(3) Receiving Premium RTI Data messages from the PGPS Server 10;

(4) Providing the PGPS Seed Data Record 30 and/or PGPS Seed Update DataRecord 36 to the PGPS Client Orbit Propagation Layer 86;

(5) Requesting RRLP Data messages from the PGPS Server 10;

(6) Receiving RRLP Data messages from the PGPS Server 10;

(7) Providing RRLP Data messages to the PGPS Client Data ManagementLayer 84.

The inputs to this layer are the following:

(1) PGPS Seed Data Record 30;

(2) PGPS Seed Update Data Record 36;

(3) RRLP Data.

The outputs of the layer are the following:

PGPS Seed Data Record 30 and PGPS Seed Update Data Record 36 (sent tothe PGPS Client Orbit Propagation Layer 86);

(2) RRLP Data messages (sent to the PGPS Client Data Management Layer84).

The PGPS Client Service Management Layer 82 will request the latest seedinformation from the PGPS Server 10, typically once every 3 days. TheRTI RRLP messages of the Premium, Advanced or Custom PGPS Service Levelswill only be requested if a notification is received from the PGPSServer 10.

PGPS Protocol

All messages between the PGPS Client Service Management Layers 82 of thePGPS Server and PGPS Client Device 20 are generally described as thePGPS Protocol 16. The PGPS Protocol 16 structure is designed to carryPGPS Seed Data Record 30, PGPS Seed Update Data Record 36 and PGPS RRLPData messages over virtually any wired or wireless bearers. By default,the PGPS Basic Service Level PGPS Protocol 16 runs on a PGPS ServiceManagement Layer HTTP Interface 56, while features of the Premium,Advanced and Custom Service Levels typically use a combination of PGPSService Management Layer HTTP Interface HTTP 56, WAP/Push 62 or SMS 64interfaces for message delivery. This section provides a description ofthe payload of each PGPS Seed Data Record 30 message when a default HTTPbearer protocol is used.

Messages from PGPS Client Software 22 consist of an HTTP GET request.Within each request is a message ID specifying which PGPS message isbeing requested. A request to get a PGPS message looks similar to thefollowing:

GET/pgpsserver/URI?cld=42&mask=1024&sld=1367&mode—1&version=1 Http/1.1

where parameters include:

cld: a unique ID for the mobile, typically, the IMSI;

(2) mask: the request mask specifying which messages are beingrequested. This mask can support a combination of PGPS Seed Data Record30, PGPS Seed Update Data Record 36 and any GRN RRLP Data messages;

(3) sld: the PGPS Seed ID contains information about the current seed inthe PGPS Client Software 22 (zero if none). The PGPS Server 10 can thenprovide the matching PGPS Server Current PGPS Seed Update Data Records80 if still available, or the PGPS Server Current PGPS Seed Data Record74.

(4) mode: a number representing the orbit prediction model in use(default=1). Additional models can be added later on, as describedherein

(5) version: the version of the client.

The HTTP response has a binary data payload that is wrapped in one XMLtag. A response will look similar to the following:

HTTP/1.1 200 OK

Content-Type: Application/Octet-Stream

Content-Length: Length of body

<RXN Mask=“1024” version=“1”>data elements in binary</RXN>

The binary payload of this message can be PGPS Seed Data Record 30, PGPSSeed Update Data Record 36 or any PGPS GRN RRLP Data informationdepending on the service level

Orbit Propagation Layer

The PGPS Client Orbit Propagation Layer 86 is the computational enginethat uses PGPS Seed Data Record 30 or PGPS Seed Update Data Record 36 topropagate the satellite orbit into the future and generates PGPS ClientPre-Generated Predicted Orbit State Vectors 106 and PGPS ClientPre-Generated Predicted Navigation Model 42 that can be supplied to theGPS/AGPS Chipset 24 & GPS/AGPS Firmware 26. The key functions of thePGPS Client Orbit Propagation Layer 86 include the following:

(1) Receiving PGPS Seed Data Record 30 and PGPS Seed Update Data Record36 from the PGPS Client Service Management Layer 82.

(2) Propagating satellite orbits forward up to n days in x epochs perday (each PGPS Client Pre-Generated Predicted Data Epochs 104 typicallybeing 15 minutes) and generate related PGPS Client Pre-GeneratedPredicted Orbit State Vectors 106;

(3) Generating PGPS Client Pre-Generated Predicted Navigation Model 108for each propagated PGPS Client Pre-Generated Predicted Orbit StateVectors 106, either ahead of time or on request.

The inputs of this layer are the following:

(1) PGPS Seed Data Record 30 or PGPS Seed Update Data Record 36.

The outputs of this layer are the following:

(1) PGPS Client Pre-Generated Predicted Orbit State Vectors 106;

(2) PGPS Client Pre-Generated Predicted Navigation Model 108.

When the PGPS Client Orbit Propagation Layer 86 receives new PGPS SeedData Record 30 or PGPS Seed Update from the PGPS Client ServiceManagement Layer 82, it will discard previously stored PGPS ClientPre-Generated Predicted Orbit State Vectors 106 and PGPS ClientPre-Generated Predicted Navigation Model 108 after it has generated newdata. New PGPS Client Pre-Generated Predicted Orbit State Vectors 106and related PGPS Client Pre-Generated Predicted Navigation Model 108 canbe generated for each satellite based on a propagation window of n hours(default n=72) with x PGPS Client Pre-Generated Predicted Data Epochs104 per hour (default x=4, i.e. 15 minutes). FIG. 9 is a tabularrepresentation of what is produced by the PGPS Client Orbit PropagationLayer 86. This pre-generation for several future PGPS ClientPre-Generated Predicted Data Epochs 104 can conveniently take place atnight or when the device is on a charger and not otherwise in use. Itthen allows for a simple lookup of the applicable PGPS ClientPre-Generated Predicted Orbit State Vectors 106 or PGPS ClientPre-Generated Predicted Navigation Model 108 record when needed for agiven epoch.

Alternatively, new PGPS Client Pre-Generated Predicted Orbit StateVectors 106 and related PGPS Client Pre-Generated Predicted NavigationModel 108 can be computed generated on request for each satellite basedon a specific propagation epoch.

Data Management Layer

The PGS Client Data Management Layer 84 handles the data produced by thePGPS Client Orbit Propagation Layer 86 as well as the GRN data messagesprovided through the Premium, Advanced or Custom PGPS Service Levels Thekey functions of this layer include the following.

(1) Receiving GRN RRLP messages from the PGS Client Service ManagementLayer 82;

(2) Storing the GRN RRLP messages

(3) Receiving PGPS Client Pre-Generated Predicted Orbit State Vectors106 and related PGPS Client Pre-Generated Predicted Navigation Model 108records from the PGS Client Orbit Propagation Layer 86;

(4) Storing PGPS Client Pre-Generated Predicted Orbit State Vectors 106and related PGPS Client Pre-Generated Predicted Navigation Model 108records that are younger than n hours;

(5) Expiring PGPS Client Pre-Generated Predicted Orbit State Vectors 106and related PGPS Client Pre-Generated Predicted Navigation Model 108records that are older than n hours;

(6) Providing the PGPS Client AGPS Interface Layer 90 with the requestedPGPS Client Pre-Generated Predicted Navigation Model 108 records fromthe applicable current PGPS Client Pre-Generated Predicted Data Epoch104;

(7) Providing the PGPS Client AGPS Interface Layer 90 with the requestedGRN RRLP message.

The inputs to this layer are the following:

(1) PGPS Client Pre-Generated Predicted Orbit State Vectors 106;

(2) PGPS Client Pre-Generated Predicted Navigation Model 108,

(3) GRN RRLP messages.

The outputs of this layer are the following:

(1) PGPS Client Pre-Generated Predicted Navigation Model 108 records forall satellites;

(2) GRN RRLP messages AGPS Interface Layer

This is where most of the actual PGPS Client Software 22 codeintegration takes place when porting the service to a new device. ThePGPS Client AGPS Interface Layer 90 services requests from the onboardGPS/AGPS Chipset 24 & GPS/AGPS Firmware 26, either directly, or throughthe PGPS Client micro-SUPL Server 92 Layer. The key functions of thislayer include:

(1) Receiving requests from the GPS/AGPS Chipset 24, either via the PGPSClient Direct API Integration Protocol 94 to the GPS/AGPS Firmware 26,or indirectly via PGPS Client Standard SUPL Messages Subset 96 betweenthe PGPS Client Micro-SUPL Server Layer 92 and PGPS Client AGPS SUPLClient 28 if present;

(2) Retrieving requested information from the PGPS Client DataManagement Layer 84;

(3) Sending the requested information to the GPS/AGPS Chipset 24, eithervia the PGPS Client Direct API Integration Protocol 94 to the GPS/AGPSFirmware 26, or indirectly via PGPS Client Standard SUPL Messages Subset96 between the PGPS Client micro-SUPL Server Layer 92 and AGPS SUPLClient 28 if present;

The inputs to this layer are

(1) Requests from the GPS/AGPS Firmware 26 or PGPS Client Micro-SUPLServer Layer 92;

(2) PGPS Client Pre-Generated Predicted Navigation Model 108 records;

(3) GRN RRLP messages.

The outputs of this layer are:

(1) PGPS Client Pre-Generated Predicted Navigation Model 108;

(2) GRN RRLP messages Micro-SUPL Protocol

New mobile devices equipped with positioning capabilities alsoincorporate support for the SUPL standard within their GPS/AGPS Firmware26. The SUPL Standard Protocol 98 dictates how, among other things, GPSassistance data can passed from a SUPL AGPS Server 102 to an AGPSdevice. As such, mobile device vendors seeking to comply with the SUPLstandard must implement an AGPS SUPL Client 28 within the device. ThisAGPS SUPL client 28 is built on top of the GPS/AGPS Firmware 26 thatinterfaces to the GPS/AGPS Chipset 24 itself.

The PGPS Client Software 22 includes can be efficiently integrated withexisting SUPL-compliant devices by channeling PGPS Client Pre-GeneratedPredicted Navigation Model 108 and optional GRN RRLP Data via thisstandard SUPL framework rather than via the GPS/AGPS Chipset 24'sGPS/AGPS Firmware 26 proprietary API.

Within the PGPS Client AGPS Interface Layer 90 discussed above, thecomponent that services SUPL requests from the GPS/AGPS Chipset 24 &GPS/AGPS Firmware 26 is called the PGPS Client micro-SUPL Server 92 (seeFIG. 8). The standard SUPL Protocol 98 does not explicitly support thenotion of a device-based SUPL AGPS server of GPS assistance data. Thestandard SUPL Protocol 98 only contemplates a remote SUPL AGPS Server102, whether located within the home mobile network (i.e. an H-SLP) orin the visited mobile network (i.e. a V-SLP). However, the PGPS Clientmicro-SUPL Server 92 in the PGPS System can appear as a SUPL AGPS Serverto the PGPS Client AGPS SUPL Client 28 if the latter is configured toreceive its GPS assistance data from a “local” SUPL AGPS server source.In other words, the PGPS Client micro-SUPL Server 92 can be seen as anSLP since it can mimic the core set of H-SLP/V-SLP functionality. In allSET (e.g., SUPL-enabled terminal) initiated use cases the followingmessages are used to communicate with the SET (SUPL enabled terminal).

(1) SUPL START

(2) SUPL RESPONSE

(3) SUPL POS INIT

(4) SUPL POS

(5) SUPL END

Therefore, the PGPS Client micro-SUPL Server Layer 92 supports a limitedlocalized SUPL service. The PGPS Client micro-SUPL Server Layer 92implements the following services:

(1) Receive and process SUPL START method

(2) Send the SUPL RESPONSE message;

(3) Receive and process the SUPL POS INIT message;

(4) Send the SUPL POS message;

(5) Send the SUPL END message.

(6) Receive and process the SUPL END message. Configuration Layer

Each layer in the PGPS Client Software 22 contains specificconfiguration parameters that govern the operation of the system. ThePGPS Client Configuration Layer 88 key function is to record and applythese parameters to each of the PGPS Client Software 22 layers.

(1) Service Management Layer Configuration

The PGPS Client Service Management Layer 82 has a configurable settingthat determines how frequently the latest PGPS Seed Data Record 30 orPGPS Seed Data 36 is requested from the PGPS Server 10.

(2) Orbit Propagation Layer Configuration

Several parameters affect when the PGPS Client Orbit Propagation Layer86 will run and how much propagation data is produced. The number ofPGPS Client Pre-Generated Predicted Orbit State Vectors 106 and PGPSClient Pre-Generated Predicted Navigation Model 108 records isconfigurable. The duration of the PGPS Client Pre-Generated PredictedData Epochs 104 is configurable Data Transfer Comparisons

FIGS. 4A-4C show different data transfer requirements comparisonsbetween this PGPS System and conventional predicted GPS systems over atypical weekly period. While the predicted orbit accuracy degradationwill typically induce device position accuracy error increments of 1-3meters per day for both system types, the present PGPS system representsdata transfer savings of 73% to 96% compared with conventional predictedGPS systems over similar prediction time periods.

Accordingly, while this invention has been described with reference toillustrative embodiments, this description is not intended to beconstrued in a limiting sense. Various modifications of the illustrativeembodiments, as well as other embodiments of the invention, will beapparent to persons skilled in the art upon reference to thisdescription. It is therefore contemplated that the appended claims willcover any such modifications or embodiments as fall within the truescope of the invention.

1-20. (canceled)
 21. A system for predicting an orbit of a satellite, the system comprising: a server; a device in communication with the server, the device receiving from the server by one of: push, poll and push and poll, an initial satellite position and velocity and force model parameters, the device generating a predicted orbital state vector using the initial satellite position and velocity and force model parameters.
 22. A system as claimed in claim 21, wherein the initial satellite position and velocity and force model parameters are received by push.
 23. A system as claimed in claim 21, wherein the initial satellite position and velocity and force model parameters are received by WAP push.
 24. A system as claimed in claim 21, wherein the initial satellite position and velocity and force model parameters are received by SMS.
 25. A system as claimed in claim 21, wherein the device generates satellite navigation data using the predicted orbital state vector, the satellite navigation data valid for a time period.
 26. A system as claimed in claim 22, wherein an update is received at the device, the update comprising parameters calculated to compensate for accuracy degradation of the predicted orbital state vector over time.
 27. A method of predicting an orbit of a satellite on a device, the method comprising: receiving, by one of: push, poll and push and poll, an initial satellite position and velocity and force model parameters; and generating a predicted orbital state vector using an initial satellite position and velocity and force model parameters.
 28. A method as claimed in claim 27, wherein the initial satellite position and velocity and force model parameters are received by push.
 29. A method as claimed in claim 27, wherein the initial satellite position and velocity and force model parameters are received by WAP push.
 30. A method as claimed in claim 27, wherein the initial satellite position and velocity and force model parameters are received by SMS.
 31. A method as claimed in claim 27, wherein the device generates satellite navigation data using the predicted orbital state vector, the satellite navigation data valid for a time period.
 32. A method as claimed in claim 28, comprising receiving an update at the device, the update comprising parameters calculated to compensate for accuracy degradation of the predicted orbital state vector over time.
 33. A device, comprising: a processor for receiving initial satellite position and velocity and force model parameters by one of: push, poll and push and poll, and for generating a predicted orbital state vector using the initial satellite position and velocity and force model parameters, the predicted orbital state vector usable for generating predicted satellite navigation data; and a GNSS receiver in communication with the processor for receiving the broadcast satellite navigation data, the broadcast satellite navigation data valid for a time period, and using the predicted satellite navigation data when no valid broadcast satellite navigation data is available.
 34. A device as claimed in claim 33, wherein the initial satellite position and velocity and force model parameters are received by push.
 35. A device as claimed in claim 33, wherein the initial satellite position and velocity and force model parameters are received by WAP push.
 36. A device as claimed in claim 33, wherein the initial satellite position and velocity and force model parameters are received by SMS.
 37. A device as claimed in claim 33, wherein the device is a mobile device.
 38. A mobile device comprising: a processor for generating a predicted orbital state vector using an initial satellite position and velocity and force model parameters, the predicted orbital state vector being used to generate satellite navigation data; and a GNSS receiver in communication with the processor for receiving the satellite navigation data; wherein the satellite navigation data is valid for a time period.
 39. A mobile device as claimed in claim 38, wherein the device is a mobile network connected device.
 40. A mobile device as claimed in claim 38, wherein the initial satellite position and velocity and force model parameters are received from a server prior to generation of the predicted orbital state vector. 